Medical device

ABSTRACT

A powered system includes a parent module including a first battery storing a charge and a child module including a second battery storing a charge and a controller. When the parent module and the child module are in electrical communication, the controller is configured to receive power from the parent module. When the charge in the parent module is depleted, the controller is configured to backfeed power from the child module to the parent module.

BACKGROUND

Medical devices can include displays, pumps, batteries and printedcircuit boards. As those components are made smaller and the device sizedecreases, design costs and repair costs can increase. Additionally,some components can cause electromagnetic interference that can detractfrom the performance of the medical device.

DESCRIPTION OF THE FIGURES

FIG. 1 a block diagram of a wireless healthcare system.

FIG. 2 illustrates an example medical device of FIG. 1.

FIG. 3 illustrates another example medical device of FIG. 1.

FIG. 4 illustrates a block diagram of an example medical device.

FIG. 5 illustrates the components of an example carrier assembly.

FIG. 6 illustrates an example power management system.

FIG. 7 illustrates example components of a display.

FIG. 8 illustrates a different view of the components shown in FIG. 7.

FIG. 9 is a block diagram illustrating physical components of acomputing device with which examples and embodiments of the disclosurecan be practiced.

FIG. 10 is a block diagram of an example electromagnetic interference(EMI) suppression system.

FIG. 11 illustrates an embodiment of the example EMI suppression systemshown in FIG. 10.

FIG. 12 illustrates an exploded view of the embodiment of the exampleEMI suppression system shown in FIG. 11.

FIG. 13 illustrates a top plan view of the embodiment of the example EMIsuppression system shown in FIG. 11.

FIG. 14 illustrates a bottom plan view of the embodiment of the exampleEMI suppression system shown in FIG. 11.

FIG. 15 illustrates a right side view of the embodiment of the exampleEMI suppression system shown in FIG. 11.

FIG. 16 illustrates a front view of the embodiment of the example EMIsuppression system shown in FIG. 11.

FIG. 17 is a block diagram of an example power management system.

FIG. 18 illustrates an embodiment of a child module in the example powermanagement system shown in FIGS. 6 and 17.

FIG. 19 illustrates an embodiment of a parent module in the examplepower management system shown in FIGS. 6 and 17.

FIG. 20 illustrates an embodiment of the example carrier assembly shownin FIG. 5 mounted to an example main printed circuit assembly.

FIG. 21 illustrates a top plan view of the embodiment shown in FIG. 20.

FIG. 22 illustrates a rear plan view of an embodiment of example fronthousing.

FIG. 23 illustrates a rear perspective view of the embodiment of examplefront housing shown in FIG. 22.

FIG. 24 illustrates a front plan view of the embodiment of example fronthousing shown in FIG. 22.

FIG. 25 illustrates a bottom plan view of the embodiment of examplefront housing shown in FIG. 22.

FIG. 26 illustrates an embodiment of an example liquid crystal display(LCD) assembly mounted to a printed circuit assembly (PCA).

FIG. 27 illustrates a front perspective view of the embodiment ofexample LCD assembly mounted to the PCA.

FIG. 28 illustrates a side view, along axis A-A in FIG. 26, of theembodiment of example LCD assembly mounted to the PCA.

FIG. 29 illustrates a top view, along axis B-B in FIG. 26, of theembodiment of example LCD assembly mounted to the PCA.

DETAILED DESCRIPTION

Health care environments can include hospitals, clinics, managed carefacilities, and other locations where medical care is provided. Medicalpersonnel in health care environments can utilize vital signs monitoringdevices, vital signs displays, personal computing devices and electronicmedical record access portals. Medical staff and providers often need torecord a patient's vital signs and enter those vital signs into thepatient's electronic medical record. Currently, providers must performvital signs measurements, remember the measurements, and then enterthose measurements into one or more computing devices which may or maynot be directly linked to the patient's electronic medical record.

FIG. 1 illustrates a block diagram of an example wireless health carenetwork 110. The example network 110 includes medical devices 103 and104, wireless computing devices 108 and 109, and communication network110. In embodiments, the example network 110 can include more or fewermedical devices 103 and 104. In embodiments, the example network caninclude more or fewer wireless computing devices 108 and 109. Thecommunication network 110 can be a wireless network, such as WiFi,Bluetooth, Zigbee, Ant, Z-Wave, etc.

In some embodiments, the one or more medical devices 103 and 104 caninclude one or more vital signs measurement components. For example, themedical devices 103 can include, for example, a thermometer, a heartrate monitor, a pulse oximeter, a non-invasive blood pressure monitor,and a respiration rate monitor. In embodiments, one or more vital signsmeasurement components are wirelessly linked to the medical devices 103and 104 and can transmit measurements to the medical devices 103 and104.

Example computing components of medical devices 103 and 104 are shownand described in more detail with reference to FIG. 9, below.

In some embodiments, the one or more wireless computing devices 108 and109 can be smart phones, tablet computers, personal digital assistants,laptop computers, and desktop computers, which can optionally be mountedon portable carts. Example computing components of the one or morewireless computing devices 108 and 109 are shown and described in moredetail with reference to FIG. 9, below. The use of less complicatedwireless computing devices 108 and 109, such as heart rate monitors,pulse oximeters, etc., is also contemplated by this document.

FIG. 2 illustrates one example of the medical device 105. The medicaldevice 105 is shown on a mobile cart, and the medical device 105 isprogrammed to provide the functionalities described herein, which caninclude, but are not limited to, vital signs monitoring. The medicaldevice 105 includes a user interface, such as a touch screen, andincludes the ability to execute multiple workflows or profiles. In someembodiments, the medical devices 105 and 106 in FIGS. 2 and 3 are themedical device 103 or 104 shown in, and described with reference to,FIG. 1. Other embodiments can include more or fewer components thanthose shown in FIG. 2, or include different components that accomplishthe same or a similar function.

The medical device 105 is able to operate within one or more profiles. Aprofile is a series of one or more tasks that a user of the medicaldevice 105 performs. When the medical device 105 operates within aprofile, the medical device 105 provides functionality suitable forassisting the user in performing the profile. When the medical device105 operates within different profiles, the medical device 105 providesdifferent functionality.

When the medical device 105 is manufactured, the medical device 105 isconfigured to be able to operate within one or more profiles. After themedical device 105 is manufactured, the medical device 105 can bereconfigured to operate within one or more additional profiles. In thisway, a user can adapt the medical device 105 for use in differentprofiles as needed.

In various embodiments, the medical device 105 operates within variousprofiles. For example, in some embodiments, the medical device 105 canoperate within a monitoring profile or a non-monitoring profile. Exampletypes of non-monitoring profiles include, but are not limited to, a spotcheck profile and an office profile. An example of a monitoring profileincludes, but is not limited to, an intervals profile.

An additional example of the medical device 106 is shown in FIG. 3. Inthis example, the medical device 106 is similar to that of the medicaldevice 105 described above. In embodiments, the medical device 106 ismounted on a wall. The medical device 106 is programmed in a mannersimilar to that described above to monitor physiological parameters of apatient. In some embodiments, the medical device 106 is a stand-alonedevice, which can mean that is not part of a mobile cart and it is notpart of a wall-mounted station.

In the examples described herein, the medical devices 104, 105, 106 arecomputing devices that have been programmed to perform special, complexfunctions. These specially-programmed devices function to manipulate andprovide data to the users in an improved form factor and with greaterefficiency.

For example, as described further below, the medical devices 104, 105,106 are specially programmed to provide the user with an improvedinterface that allows the user to discern important information at aglance. This improved interface removes unnecessary information andcontrols so that the data that is important can be more efficiently andeasily viewed, particularly when the user is positioned at a distancefrom the medical device.

In the examples described herein, the medical devices 104, 105, 106 arecomputing devices that have been programmed to perform special, complexfunctions. These specially-programmed devices function to manipulate andprovide data to the users in an improved form factor and with greaterefficiency.

For example, as described further below, the medical devices 104, 105,106 are specially programmed to provide the user with an improvedinterface during initial use of the devices. This allows the user tomore efficiently select a profile for controlling the functionality ofthe device.

In addition, the medical devices 104, 105, 106 are specially programmedto assist the users once vital signs information is captured from thepatients. For example, the devices are programmed to more efficientlyand easily capture additional contextual information that is needed whensaving vital signs data to a permanent record, such as an EMR record.This is accomplished using an interface that is more intuitive androbust.

The medical devices 104 and 105 shown in FIGS. 2 and 3 are only examplesof a medical device. In some examples described herein, the medicaldevices 104 and 105 are portable devices. In other examples, the medicaldevices 104 and 105 are non-portable devices, such as computing deviceslike workstations. All different types of medical devices used tocollect patient data can be used. Many configurations are possible.

An example medical product system 100 is shown in FIG. 4. The examplemedical product system 100 includes the medical device 104 that can havea carrier assembly 200, power management module 300, electromagneticinterference (EMI) suppression module 400, and display 500. Otherembodiments may include more or fewer components.

FIG. 5 illustrates an example embodiment of the carrier assembly 200that can be mounted to a main printed circuit assembly (PCA) 290 of themedical device 104. FIGS. 20 and 21 illustrate the example embodiment ofcarrier assembly 200 mounted to a PCA 290. The example assembly 200 caninclude a plastic carrier 201 supporting a pump 202, pump retentionsnaps 204, valves 206, a wire routing feature 208, a WiFi radio 210, aBluetooth radio 218, a speaker 212, and an integrated pump/valve harness220. A manifold 214 can be in communication with the pump 202 and ablood pressure (BP) cuff port 230. FIGS. 20 and 21 illustrateembodiments of a main printed circuit assembly 290 including the exampleembodiment of carrier assembly 200. Other embodiments can include moreor fewer components.

The example carrier assembly 200 consolidates the blood pressurepneumatic system that includes a pump 202, a solenoid valve 206 and acheck valve 224. The pneumatic system can be supported by a plasticcarrier 201. As shown, the main printed circuit assembly 290 has a topsurface area that supports and houses various components, including thecarrier assembly 200. The carrier assembly 200 occupies an amount ofsurface area on the top surface area of the main printed circuitassembly 290 that is at least less than 50% of the top surface area; atleast less than 40% of the top surface area; at least less than 33% ofthe top surface area; at least less than 25% of the top surface area; orat least less than 20% of the top surface area.

In embodiments, the pump 202, solenoid valve 206 and check valve 224 areall in fluid communication with each other and with one or more pressuretransducers through a single manifold 214. Manifold 214 also interfaceswith the blood pressure cuff port 230.

In embodiments, the example carrier assembly 200 provides a single partthat provides mounting for the pump 202 and valves 206. In someembodiments, the example carrier assembly 200 includes features formanaging electrical wire routing for the pump and valve wires, such asharnesses, slots, snaps, mounts, ports, and other components known inthe art. Wire routing feature 208 and integrated pump/valve harness 220are examples of features for managing wire routing for the pump andvalve wires.

In some embodiments, the example carrier assembly 200 includes mountsfor a speaker 212, a WiFi radio 210 and/or a Bluetooth radio 218. Themounts can include slots in the assembly 200, harnesses, snaps,recesses, or other components known in the art.

FIGS. 6 and 17-19 illustrate an example power management system 300. Theexample system 300 includes a parent module 320 and a child module 350,each with input power connectors and connected by wire 372. Parentmodule 320 and child module 350 are the medical devices shown in FIGS. 2and 3, although the example power management system 300 can be used inother environments. Power management system 300 extends the operationaltime beyond the battery capacity of the parent module 320. Inembodiments, the child input power connector has exposed pins when theconnector is unconnected. An embodiment of example child module 394 isshown in FIG. 18 and an embodiment of example parent module 396 is shownin FIG. 18. Other embodiments can include more or fewer components.

The example system 300 can be configured to run on mains power, whereinthe parent module 320 and the child module 350 can be poweredindefinitely. In the example system 300, the parent module 320 isresponsible for charging the battery of the child module 350 when thechild module 350 is not connected to mains power. The parent module 320can also be responsible for providing operational power to the childmodule 350. This is depicted in FIG. 17 as normal mode 380: powerflowing from parent module 320 to child module 350.

In embodiments, parent module 320 includes a larger battery than childmodule 350. For example, parent module 320 includes a 9 cell battery andchild module 350 includes a 2 cell battery. Other configurations arepossible.

In embodiments, when running on battery power, the parent module 320continues to charge the child module's 350 battery. This is shown asnormal mode 380 in FIG. 17. In some embodiments, it is likely that thechild module's 350 battery is powered from the time spent on mainspower. In embodiments, the parent module's 320 battery expires. At thatpoint, the example system 300 deploys a backfeed function, shown asbackfeed mode 390 in FIG. 17, that allows power to flow both ways in theinterface between the parent module 320 and the child module 350. Inembodiments, the backfeed mode 390 enables the system to continue tooperate on the child module's 350 battery after the parent module's 320battery is exhausted. In embodiments, this configuration can maximizebattery life in contrast to non-backfeed configurations.

In embodiments, the child module 350 can operate stand-alone. Inembodiments, the connector on the child module 350 that connects to theparent module 350 is large enough to expose the connector pin. Exposinga powered pin can produce an unsafe and undesirable situation.

In embodiments, when the child module 350 is not connected to the parentmodule 320, the child module's 350 system detects that the pin isdisconnected. When the system detects that the pin is disconnected, thechild module's 350 system de-energizes the power pin on the child module350.

A wire 372 used to convey power from the parent module 320 to the childmodule 350 (normal mode 380) is also used to convey power from the childmodule 350 to the parent module 320 (backfeed module). A battery lifestatus 124 shown on a display of child module 350, an example embodimentof which is shown in FIG. 3, includes the combined battery life usingbackfeed mode 390 when the parent module 320 is connected to the childmodule 350.

The example medical device 104 can also optionally include anelectromagnetic interference (EMI) suppression module 400. In somemedical devices, sensitive signals in a printed circuit board are buriedon inner layers. These signals can go to an external shielded cable.Examples include SpO2, electroencephalograph (EEG), electrocardiograph(ECG), etc. These cables can act as antennas for unwantedelectromagnetic interference, such as radio frequency interference(RFI), that is both radiated from and induced into the device.

The example EMI suppression 400 includes applying a ferrite to surrounda printed circuit board. In embodiments, the ferrite is wrapped around abare printed circuit board, or surrounds part of a printed circuitboard. In embodiments, the ferrite has a geometry such that itsuppresses unwanted RFI on traces on inner and/or outer layers of theprinted circuit assembly.

FIG. 10 is a schematic block diagram of an embodiment of EMI suppression400. Ferrite 410 is used to surround traces 404 in printed circuit board402. The traces 404 do not directly connect to the ferrite 410. Rather,the traces 404 surrounded by ferrite 410 are routed to stay within theprinted circuit board 402 and do not come up to the surface of printedcircuit board 402. Generally, signals in traces are not interrupted bylayer transitions or impedance mismatches. When passing through ferrite410, the traces 404 do not transition from their electrical shielding.

FIG. 11 illustrates a perspective view of an embodiment of the exampleEMI suppression 450 discussed in connection with FIG. 10. EMIsuppression 450 includes slots 456 in a PCB 452 that define tongue 458,and ferrite 454 surrounding a portion of the PCB 452 containing traces470. The tracings 470 are shown in phantom form to indicate that thetracings are actually below the surface of the PCB 452 in one of theinner layers. A cable connector 460 is also depicted. Other embodimentscan include more or fewer components.

FIGS. 12-16 additionally illustrate various views of the embodiment ofthe example EMI suppression 450 shown in FIG. 11. Specifically, FIG. 12is an exploded, perspective view of EMI suppression 450, FIG. 13 is atop plan view of EMI suppression 450, FIG. 14 is a bottom plan view ofEMI suppression 450, FIG. 15 is a right side view of EMI suppression450, and FIG. 16 is a front view of EMI suppression 450. Unlessotherwise noted, the following discussion is with reference to FIGS.11-16.

Surrounding traces 470 with ferrite 454 provides EMI suppression even inembodiments where a cord connecting to printed circuit board 452 doesnot include EMI suppression components. Although EMI suppression 450 isdiscussed in relation to a medical device, it can be used to suppressEMI in any PCB with a cable connection, regardless of the application.

Ferrite 454 has an annular cross-section thereby enabling it to passthrough tongue 458 and surround traces within PCB 452. In the embodimentshown, ferrite 454 has a rectangular annulus cross-section, althoughother shapes are possible. Ferrite 454 is positioned on the distal endof tongue 458 adjacent to the connector assembly 460. In embodiments,EMI suppression improves as ferrite 454 is positioned closer toconnector assembly 460. However, any position of ferrite 454 on tongue458 provides EMI suppression.

Ferrite 454 is positioned over the PCB 452 before soldering near thecable connector 460. Ferrite 454 can be secured to the PCB 452 using,for example, cloth tape.

Cable connector 460 can connect to, and receive data from, a vital signsdevice, such as an SpO2 monitor, an EEG, or other device.

In the embodiment shown, ferrite 454 has a single-piece construction.Other embodiments are contemplated where ferrite 454 is formed by morethan one piece.

Ferrite 454 surrounds the tracings within PCB 452 in at least the x-yplanes above and below PCB 452 as well as the x-z planes. Inembodiments, traces 470 carry signals that might be sensitive to noise,such as EMI, which could damage the signal's integrity. An example of asignal sensitive to noise is a peripheral capillary oxygen saturation(SpO2) signal.

An example installation of the example EMI suppression was conducted andreduced EMI. In the example installation, a printed circuit was carvedto accept a standard Ferrite. Then the cable connector was removed.Ferrite was inserted and then the connector was replaced.

FIGS. 7, 8, and 22-29 illustrate an example display 500. The exampledisplay 500 includes a printed circuit assembly (PCA) 290, a liquidcrystal display (LCD) assembly 510, a front housing 515, an elastomericbezel 520, obround slots 524 and an obround boss 525. A rear housing,not shown, mates with the front housing 515 and PCA 290. Front housing515 is also shown in FIGS. 22-25: FIG. 22 is a rear plan view of fronthousing 515, FIG. 23 is a rear perspective view of the front housing515, FIG. 24 is a front plan view of the front housing 515, and FIG. 25is a bottom plan view of the front housing 515. Printed circuit assembly290 and LCD assembly 510 are additionally shown in FIGS. 26-29: FIG. 26is a front plan view of PCA 290 and LCD assembly 510, FIG. 27 is abottom front perspective view of PCA 290 and LCD assembly 510, FIG. 28is a side view along axis A-A in FIG. 26, and FIG. 29 is a top viewalong axis B-B in FIG. 26. Other example displays can include more orfewer components than those depicted.

The example display 500 has an LCD assembly 510 mounted directly to thePCA 290. The mount enables the LCD assembly 510 to float relative to thePCA 290. Because the LCD assembly 510 can float, it can conform tofeatures in the mating front housing/bezel. In embodiments, the floatingLCD that interfaces with an elastomeric bezel 520 on the front housingseals the LCD from fluid ingress and it can provide impact resistance.

The example embodiment of the display 500 illustrated in FIGS. 7 and22-29 shows the LCD assembly 510 fastened to the PCA. The LCD assembly510 has obround bosses 525 that mate with similarly shaped but largerobround slots 524 in the printed circuit board 290. This clearance canenable the LCD assembly 510 to float in the x- and y-axes relative tothe PCA 290. The LCD assembly 510 is thereby secured to the PCA in thez-axis with, for example, screws 526 that thread into the frame bosses525, where the head diameter of the screw 526 can be larger than theslot width in the PCA 290. In embodiments, the frame bosses 525 aretaller than the thickness of the PCA 290 which can prevent the screw 526head from seating on the PCA 290 and locking the LCD assembly 510 to thePCA 290. This is illustrated in the cut-out view shown in FIG. 8, wherethe frame boss 525 is seen extending through the obround slot 524 andbeyond the PCA 290 because the frame boss 525 is taller than thethickness of the PCA 290.

Additionally, an elastomeric bezel 520 can be precisely positioned andcontained in the front housing 515 relative to the LCD opening, wherethe bezel 520 can have features that precisely locate the LCD assembly510. The floating enables the LCD to be positioned to the LCD opening inthe front housing independent of the location of the PCA, which can haveother design constraints that could add to the tolerance stackup. Inembodiments, the bezel 520 is pre-assembled to the front housing 515.

FIG. 9 is a block diagram illustrating physical components (i.e.,hardware) of a computing device 1800 with which embodiments of thedisclosure may be practiced. The computing device components describedbelow may be suitable to act as the computing devices described above,such as wireless computing device and/or medical device of FIG. 1. In abasic configuration, the computing device 1800 may include at least oneprocessing unit 1802 and a system memory 1804. Depending on theconfiguration and type of computing device, the system memory 1804 maycomprise, but is not limited to, volatile storage (e.g., random accessmemory), non-volatile storage (e.g., read-only memory), flash memory, orany combination of such memories. The system memory 1804 may include anoperating system 1805 and one or more program modules 1806 suitable forrunning software applications 1820. The operating system 1805, forexample, may be suitable for controlling the operation of the computingdevice 1800. Furthermore, embodiments of the disclosure may be practicedin conjunction with a graphics library, other operating systems, or anyother application program and is not limited to any particularapplication or system. This basic configuration is illustrated in FIG. 9by those components within a dashed line 1808. The computing device 1800may have additional features or functionality. For example, thecomputing device 1800 may also include additional data storage devices(removable and/or non-removable) such as, for example, magnetic disks,optical disks, or tape. Such additional storage is illustrated in FIG. 9by a removable storage device 1809 and a non-removable storage device1810.

As stated above, a number of program modules and data files may bestored in the system memory 1804. While executing on the processing unit1802, the program modules 1806 may perform processes including, but notlimited to, generate list of devices, broadcast user-friendly name,broadcast transmitter power, determine proximity of wireless computingdevice, connect with wireless computing device, transfer vital sign datato a patient's EMR, sort list of wireless computing devices withinrange, and other processes described with reference to the figures asdescribed herein. Other program modules that may be used in accordancewith embodiments of the present disclosure, and in particular togenerate screen content, may include electronic mail and contactsapplications, word processing applications, spreadsheet applications,database applications, slide presentation applications, drawing orcomputer-aided application programs, etc.

Furthermore, embodiments of the disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. For example, embodiments of the disclosure may bepracticed via a system-on-a-chip (SOC) where each or many of thecomponents illustrated in FIG. 9 may be integrated onto a singleintegrated circuit. Such an SOC device may include one or moreprocessing units, graphics units, communications units, systemvirtualization units and various application functionality all of whichare integrated (or “burned”) onto the chip substrate as a singleintegrated circuit. When operating via an SOC, the functionality,described herein, may be operated via application-specific logicintegrated with other components of the computing device 1800 on thesingle integrated circuit (chip). Embodiments of the disclosure may alsobe practiced using other technologies capable of performing logicaloperations such as, for example, AND, OR, and NOT, including but notlimited to mechanical, optical, fluidic, and quantum technologies. Inaddition, embodiments of the disclosure may be practiced within ageneral purpose computer or in any other circuits or systems.

The computing device 1800 may also have one or more input device(s) 1812such as a keyboard, a mouse, a pen, a sound or voice input device, atouch or swipe input device, etc. The output device(s) 1814 such as adisplay, speakers, a printer, etc. may also be included. Theaforementioned devices are examples and others may be used. Thecomputing device 1800 may include one or more communication connections1816 allowing communications with other computing devices. Examples ofsuitable communication connections 1816 include, but are not limited to,RF transmitter, receiver, and/or transceiver circuitry; universal serialbus (USB), parallel, and/or serial ports.

The term computer readable media as used herein may includenon-transitory computer storage media. Computer storage media mayinclude volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, or program modules.The system memory 1804, the removable storage device 1809, and thenon-removable storage device 1810 are all computer storage mediaexamples (i.e., memory storage.) Computer storage media may include RAM,ROM, electrically erasable read-only memory (EEPROM), flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other article ofmanufacture which can be used to store information and which can beaccessed by the computing device 1800. Any such computer storage mediamay be part of the computing device 1800. Computer storage media doesnot include a carrier wave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, andincludes any information delivery media. The term “modulated datasignal” may describe a signal that has one or more characteristics setor changed in such a manner as to encode information in the signal. Byway of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), infrared, andother wireless media.

Although the example medical devices described herein are devices usedto monitor patients, other types of medical devices can also be used.For example, the different components of the CONNEX™ system, such as theintermediary servers that communication with the monitoring devices, canalso require maintenance in the form of firmware and software updates.These intermediary servers can be managed by the systems and methodsdescribed herein to update the maintenance requirements of the servers.

Embodiments of the present invention may be utilized in variousdistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network in adistributed computing environment.

The block diagrams depicted herein are just examples. There may be manyvariations to these diagrams described therein without departing fromthe spirit of the disclosure. For instance, components may be added,deleted or modified.

While embodiments have been described, it will be understood that thoseskilled in the art, both now and in the future, may make variousimprovements and enhancements can be made.

What is claimed is:
 1. A powered system, comprising: a parent moduleincluding a first battery storing a charge; and a child module includinga second battery storing a charge and a controller, wherein when theparent module and the child module are in electrical communication, thecontroller is configured to receive power from the parent module;wherein, when the charge in the parent module is depleted, thecontroller is configured to backfeed power from the child module to theparent module; wherein the child module further includes one or moremale connector pins configured to mate with a female connector, andwherein the controller is configured to de-energize the one or more maleconnector pins when the controller detects that the child module is notconnected to the female connector; wherein the child module furtherincludes a display, wherein the child module is configured to receivevital sign data, and wherein the child module is configured to displaythe vital sign data; and wherein the display includes an expectedbattery life display, the expected battery life display indicating theexpected battery life including both the first battery and the secondbattery.
 2. The powered system of claim 1, wherein the first batterycomprises a nine-cell battery, and wherein the second battery comprisesa two-cell battery.
 3. The powered system of claim 1, wherein thepowered system, when the child module is connected to a mains powersource, is powered exclusively off the mains power source, and when thechild module is unconnected to the mains power source, the poweredsystem initially is powered exclusively off the first battery.
 4. Thepowered system of claim 1, wherein the powered system, when the childmodule is connected to a mains power source, is powered exclusively offthe mains power source, and when the child module is unconnected to themains power source, the powered system initially is powered exclusivelyoff the first battery.
 5. A medical device, comprising: a parent moduleincluding a first battery; a child module including a second battery anda controller, the child module configured to receive vital signs data,wherein the parent module and the child module are in electricalcommunication, the controller is configured to receive power from theparent module; and wherein when a charge in the first battery isdepleted, the controller is configured to backfeed power from the childmodule to the parent module; wherein the child module further includesone or more male connector pins configured to mate with a femaleconnector, and wherein the controller is configured to de-energize theone or more male connector pins when the controller detects that thechild module is not connected to the female connector; wherein the firstbattery comprises a nine-cell battery, and wherein the second batterycomprises a two-cell battery; wherein the child module further includesa display, and wherein the child module is configured to display thevital sign data on the display; and wherein the display includes anexpected battery life display, the expected battery life displayindicating the expected battery life including both the first batteryand the second battery.
 6. The medical device of claim 5, wherein themedical device, when the child module is connected to a mains powersource, is exclusively powered off the mains power source; and when thechild module is unconnected to the mains power source, the medicaldevice initially is powered exclusively off the first battery.
 7. Themedical device of claim 5, wherein the medical device, when the childmodule is connected to a mains power source, is powered exclusively offthe mains power source, and when the child module is unconnected to themains power source, the medical device initially is powered exclusivelyoff the first battery.
 8. A method of powering a medical device, themethod comprising: providing a parent module including a first batterystoring a charge; and providing a child module including a secondbattery storing a charge and a controller, when the parent module andthe child module are in electrical communication, powering thecontroller from the parent module; when the charge in the parent moduleis depleted, backfeeding power from the child module to the parentmodule; receiving vital sign data; displaying the vital sign data; anddisplaying an expected battery life display, the expected battery lifedisplay indicating the expected battery life including both the firstbattery and the second battery.
 9. The method of claim 8, furthercomprising: when the child module is connected to a mains power source,powering the medical device exclusively off the mains power source; andwhen the child module is unconnected to the mains power source,initially powering the medical device exclusively off the first battery.